Managing improvement ideas effectively [webinar]

Most organisations want their employees to suggest improvements — but few have a reliable system for acting on those ideas. This webinar covers why the traditional suggestion box fails, what a proper improvement loop actually looks like, and how Gluu’s change suggestion feature helps you close the gap.

Watch the full webinar below, or read the key takeaways to get the essentials in a few minutes.

Why employee-driven improvements matter

Most organisations assume that management has the clearest view of what needs to change. In practice, the opposite is true. Frontline employees — the people doing the actual work — hold the majority of operational knowledge in any company. They see the daily friction, the workarounds, and the small inefficiencies that never make it into a board report.

Louisa, Gluu’s Customer Success Manager and a former quality manager with five years of factory floor experience, describes this as the iceberg problem: top management only sees a small fraction of what is actually happening. The rest stays submerged — unless there is a formal channel to surface it.

Furthermore, the real value of employee-driven improvements is not in any single idea. It is in the accumulation of many small, frequent changes over time. A continuous flow of incremental improvements consistently outperforms the occasional large consulting project — and at a fraction of the cost. As Louisa explains in the webinar, this does not mean external consultants are never useful. For major structural changes, outside perspective is genuinely valuable. But if small day-to-day improvements are never captured, organisations leave significant growth potential on the table.

This thinking is central to Lean philosophy: empower the people closest to the customer or the value-adding work to identify and solve problems, and treat every problem surfaced as a learning opportunity rather than a complaint.

The improvement ideas that constantly flow from our employees are all reported digitally, picked up by process owners, and some incorporated back into our management system.

Hans Jørgen Ebbesen, CEO, CJ A/S

Why the suggestion box fails

The problem is not that employees lack good ideas. The problem is that the most common approaches to collecting those ideas — suggestion boxes, sticky notes on a team lead’s desk, emails to a manager — are structurally broken.

Consider what typically happens. An employee notices an issue while working. They write a note or send an email. Days later, someone else tries to understand the suggestion without any of the original context. They do not know which process it refers to, which step in the workflow caused the problem, or what the employee was actually trying to convey. The suggestion either gets misunderstood or quietly dropped.

Even worse, the employee who submitted the idea usually never hears anything back. They do not know whether the suggestion was read, rejected, or implemented. That silence is discouraging — and it is one of the main reasons employees stop making suggestions in the first place.

There is also a documentation problem. For organisations working under ISO standards or other compliance frameworks, continuous improvement is not optional — it is a requirement. Informal suggestion processes make it very difficult to demonstrate to an auditor that a proper improvement cycle actually took place.

The context problem

One underappreciated barrier is context. When an employee is standing at a machine and sees something that could be done better, the suggestion makes complete sense in that moment. By the time it reaches someone who can act on it — detached from the physical situation, written on a scrap of paper — that context is gone. The suggestion becomes ambiguous, and the effort required to reconstruct it is often too high.

This is also why the barrier to submitting suggestions is so high for many employees. If they have to write half a page just to explain which process they are referring to before they can even get to the actual idea, most people simply will not bother.

“The improvement ideas that constantly flow from our employees are all reported digitally, picked up by process owners, and some incorporated back into our management system.”
Read case

Hans Jørgen Ebbesen,
CEO, CJ A/S

What a proper improvement process requires

Before looking at tooling, it helps to define what a functional improvement process actually needs. Based on the discussion in the webinar, there are four core requirements.

First, it needs to be easy to submit a suggestion. The lower the friction, the more ideas come in. If employees have to fill in a long form or navigate a complex system just to flag a problem, they will not do it.

Second, every suggestion needs to be discussed in a transparent way. Employees should be able to see that their idea was received, that someone is looking at it, and that others are weighing in. This is what creates the sense that the suggestion matters — even if it is ultimately rejected.

Third, approvals and rejections both need to be communicated clearly. A suggestion that disappears into silence is almost worse than one that gets a quick “no.” When employees know the outcome, they feel heard. When they do not, they disengage.

Fourth, there needs to be sufficient documentation. Not just for compliance, but because good documentation allows the organisation to learn from its own improvement history — what was tried, what worked, what did not, and why decisions were made.

How Gluu’s change suggestion feature works

Gluu’s approach is built around one core idea: process improvement should happen in the context of the process itself. Rather than capturing suggestions in a separate tool or inbox, Gluu lets employees submit comments and improvement ideas directly within the process or work instruction they are working with.

Here is how the flow works in practice.

Submitting a suggestion

Any employee can submit a comment while viewing a process or work instruction in Gluu — whether on a desktop, a tablet, or the mobile app. Importantly, they can also attach a photo. For frontline workers at a machine or on a shop floor, this means the suggestion can include visual evidence from the actual work context, submitted in the moment rather than reconstructed later.

A comment can stay as a general observation, or it can be escalated into a formal change suggestion with a single click. The process owner decides whether to elevate it — keeping the barrier for employees as low as possible while ensuring quality control sits with the right person.

The activity feed

All comments, suggestions, approvals, and version changes appear in a unified activity feed attached to each process. This feed is visible to everyone involved in that process, which creates the transparency that informal systems cannot provide. Employees can see that their suggestion has been received. Colleagues can weigh in. Process owners can respond, ask follow-up questions, or pull in additional stakeholders by tagging them directly in the discussion.

Because all of this stays attached to the specific process or work instruction, there is no context loss. The suggestion is always read alongside the process it refers to.

Managing suggestions as a process owner

Process owners see all suggestions across their processes in one view, with filtering by status, time period, label, and role. This makes it practical to manage a high volume of ideas without losing track. Each suggestion moves through a status workflow — open, approved, implemented, or rejected — so the full lifecycle is always visible.

When a suggestion is approved, it becomes a named change suggestion with a formal reference. The editor who updates the process can then view all approved suggestions directly within the editing view, mark each one as implemented as they go, and generate an automatic summary of what changed. That summary becomes the basis for a new version, which is then published with a notification to everyone involved.

Versioning and rollback

Every version of a process and its underlying work instructions is stored in Gluu’s change log. If a change turns out to have a negative effect — on time, cost, or quality — it is possible to go back to any previous version and restore it. This makes it safe to experiment, because no change is ever permanent.

Gluu also supports QR codes that can be printed and attached to physical machines or workstations. Scanning the code opens the relevant work instruction on the employee’s phone, with the comment field immediately accessible. This closes the gap between the physical work context and the digital improvement process — making it as easy as possible for a frontline worker to flag something in the moment.

How to get started: Gluu’s recommendation

The most common mistake when rolling out a new process improvement initiative is trying to do too much at once. Gluu’s recommendation is to start small — with one team and the processes they are directly involved in. Introduce them to the way of working, encourage them to submit suggestions, and — critically — make sure every suggestion gets a response.

It does not matter whether a suggestion is implemented or rejected. What matters is that employees receive a visible response. That is what builds the habit and the trust that makes continuous improvement sustainable. Once the first group is comfortable with the process, it can be scaled to other parts of the organisation.

A useful first step is to pilot the approach within the process management team itself. This gives them firsthand experience of the flow before rolling it out more broadly — and often surfaces useful improvements to the process itself before it reaches a wider audience.

Want to go further? Our guide to process improvement methods, examples and best practice covers the full landscape — tools, frameworks, and real-world cases to help you build a continuous improvement culture.

FAQ – managing process improvement ideas